Node / meshtastic / Meshtastic-Android / files / specs / 20260507-161758-node-list-layout / quickstart.md

Displaying Rendered • View raw • Download

This guide helps a Meshtastic-Android contributor bootstrap, navigate, test, and debug the Node List Layout feature.

• JDK 21

• Android SDK installed and T383838ANDROID_HOME available to Gradle

• Git submodule initialized for T383838core/proto

• A working T383838local.properties file (copy from T383838secrets.defaults.properties if needed)

T282828

Tff7b72[ -f local.properties Tff7b72] Tff7b72|| cp secrets.defaults.properties local.properties

Once implemented, the feature is accessible at:

• Settings UI: Settings > App Settings > Node Layout

• Node List: The Nodes tab renders rows based on the selected density

No new navigation routes or deep links are required.

T282828

T282828

T282828

./gradlew spotlessApply detekt assembleDebug Tffa657test allTests

T282828

1. Start with preferences — add DataStore keys in T383838UiPrefsImpl.kt and verify defaults with a unit test.

2. Build the compact composable — create T383838NodeItemCompact.kt with hardcoded toggles first, then wire to DataStore.

3. Wire the list — modify T383838NodeListScreen.kt to switch between T383838NodeItem and T383838NodeItemCompact.

4. Build settings UI — create T383838NodeLayoutSettings.kt with the picker, toggles, and live preview.

5. Add the help sheet — create T383838NodeListHelp.kt with signal strength documentation.

6. Test — run T383838allTests for both T383838feature:node and T383838feature:settings.

• Toggle not persisting: Check that the DataStore key string matches T383838NodeListLayoutPreferences enum value exactly.

• Chip size wrong: Verify T383838lineCount derivation — it counts toggle state, not data presence.

• Live preview empty: The preview requires at least one node in the Room database. Connect to a radio or use test fixtures.

• LazyColumn jank: Ensure stable T383838key parameters are set on T383838LazyColumn items. Profile with Layout Inspector if needed.

This feature does not require custom logging beyond standard Compose recomposition debugging. Use Android Studio Layout Inspector to diagnose rendering issues.